Determination of SSB/RMSI periodicity for IAB node

ABSTRACT

An IAB node performs a method for determining a periodicity of a SSB and/or a RMSI for use in an IAB backhaul link. The method may comprise one or more of: using a predetermined periodicity value; determining a periodicity value based on at least one different parameter; receiving a signaling message indicating a periodicity value and using the indicated periodicity value for the IAB backhaul link; and selecting a periodicity value from a plurality of permitted periodicity values.

PRIORITY

This nonprovisional application is a U.S. National Stage Filing under 35U.S.C. § 371 of International Patent Application Serial No.PCT/CN2019/113401 filed Oct. 25, 2019 and entitled “Determination ofSSB/RMSI Periodicity for IAB Node” which claims priority to PCTInternational Patent Application No. PCT/CN2019/071440 filed Jan. 11,2019 both of which are hereby incorporated by reference in theirentirety.

TECHNICAL FIELD

Embodiments described herein relate to methods and apparatus for use inintegrated access and backhaul.

BACKGROUND

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

General Introduction of the Initial Access of IAB Node

In a multi-hop wireless relay network, some User Equipments (UEs)connect to the network via relay nodes over more than one hop. In FIG. 1, a multi-hop integrated access and backhaul (IAB) deployment ispresented, where the IAB donor node (in short IAB donor) has a wiredconnection to the core network and the IAB relay nodes (in short IABnodes) are wirelessly connected to the IAB donor as child nodes, eitherdirectly (single hop) or indirectly via other IAB nodes (multi-hop). Theconnection between IAB donor/node and UEs is called access link, whereasthe connection between two IAB nodes or between an IAB donor and an IABnode is called backhaul link. For the IAB network, the backhaul linksare realized as NR wireless links. The IAB donor and some of the IABnodes serve not only the UE traffic within the serving range over theaccess link, but also the aggregated traffic from/to their child nodesover the backhaul link.

When an IAB node is turned on, its parent node, i.e. which node (forexample, a donor node in case of single hop or another already connectedIAB node in case of multi-hop) to eventually connect to, needs to bedecided. For example, in the case of FIG. 1 , the IAB node 2 (IAB-N2)can either connect to IAB-N1 or directly to the IAB donor (IAB-DN). Theconnection determination of each IAB node forms a certain topologybetween the IAB donor and IAB nodes that impacts on the achievableperformance of the UEs.

For different reasons, an already connected IAB node may also,potentially, have to change its connection to a different parent node.

The Mobile-Termination (MT) function has been defined as a component ofan IAB node. In the context of the IAB study, MT is referred to as afunction residing on an IAB-node that terminates radio interface layersof the backhaul Uu interface toward the IAB-donor or other parentIAB-nodes.

FIG. 2 shows a reference diagram for IAB in standalone mode, whichcontains an IAB-donor and multiple IAB-nodes. The IAB-donor is treatedas a single logical node that comprises a set of functions such asgNB-DU (where DU means Distribution Unit), gNB-CU-CP (where CU meansCentral Unit, and CP means Control Plane), gNB-CU-UP (where CU meansCentral Unit, and UP means User Plane), and potentially other functions.In a deployment, the IAB-donor can be split according to thesefunctions, which can all be either collocated or non-collocated asallowed by 3GPP NG-RAN architecture. IAB-related aspects may arise whensuch split is exercised. Also, some of the functions presentlyassociated with the IAB-donor may eventually be moved outside of thedonor in case it becomes evident that they do not perform IAB-specifictasks. Note that besides an IAB donor, an IAB node also has its DUfunction.

Within 3GPP discussion on IAB, the related topic of IAB-node initialaccess (stage1) and IAB-node discovery and measurement (Stage 2) arediscussed.

IAB-Node Initial Access (Stage 1):

In case of standalone (SA) deployments, initial IAB node discovery bythe MT (Stage 1) function follows the same 3GPP Rel-15 initial accessprocedure as an UE, including cell search based on the sameSynchronization Signal/Physical Broadcast Channel blocks (SS/PBCH blocksor SSBs) available for access UEs, SI (System Information) acquisition,and random access, in order to initially set up a connection to a parentIAB-node or a IAB-donor.

In case of a non-standalone (NSA) deployment, when MT function of anIAB-node performs initial access on NR carrier (however a UE performsinitial access on LTE carrier), it follows the same Stage-1 initialaccess as an accessing UE in SA deployments. The periodicity of SSB setand/or RMSI (Remaining Minimum System Information) assumed by the MTsfor initial access may be longer than 20 ms which is assumed by Rel-15UEs, and a single value is to be selected from the following candidatevalues: 20 ms, 40 ms, 80 ms, 160 ms.

Note: This implies that the candidate parent IAB-nodes/donors mustsupport both NSA functionality for the UE and SA functionality for theMT on the NR carrier.

Inter-IAB-Node Discovery and Measurement (Stage 2):

For the purpose of backhaul link reference signal receivedpower/reference signal received quality (RSRP/RSRQ) RRM measurements,IAB supports both SSB-based and CSI-RS (Channel State InformationReference Signal) based solutions.

For the purpose of inter-IAB-node and donor detection after the IAB-nodeDU becomes active (Stage 2), the inter IAB-node discovery procedureneeds to take into account the half-duplex constraint at an IAB-node andmulti-hop topologies. The following three solutions are supported:

SSB-Based Solutions (Solution 1-A and 1-B):

-   -   Solution 1-A) Reusing the same set of SSBs used for access UEs:    -   In this case, the SSBs for inter-IAB cell search in stage 2 are        on the currently defined sync raster for a SA frequency layer,        while for a NSA frequency layer the SSBs are transmitted inside        of the SMTC (SSB Measurement Time Configuration) configured for        access UEs.    -   Solution 1-B) Use of SSBs which are orthogonal (TDM and/or FDM)        with SSBs used for access UEs:    -   In this case, the SSBs, that may get muted, for inter-IAB cell        search and measurement in stage 2 are not on the currently        defined sync raster for a SA frequency layer, while for a NSA        frequency layer the SSBs are transmitted outside of the SMTC        configured for access UEs.

An IAB-node should not mute its own SSB transmissions targeting UE cellsearch and measurement when doing inter-IAB cell search in stage 2:

-   -   For SA, this means that SSBs transmitted on the currently        defined sync raster follow the currently defined periodicity for        initial access;    -   In case of Solution 1-B, this implies SSBs, that may get muted,        for inter-IAB stage 2 cell search is at least TDM with SSBs used        for UE cell search and measurements.

CSI-RS Based Solutions (Solution 2):

-   -   CSI-RS can be used for inter-IAB detection in synchronous        network

To support IAB-node initial access and Stage 2 inter-IAB-node discoveryand measurement, enhancements to existing Re1.15 SMTC/CSI-RS/RACHconfigurations and RMSI (Remaining Minimum System Information) may needto be supported as well as coordination across IAB-nodes.

SSB/RMSI Periodicity in NR Release 15

A UE can be provided per serving cell by higher layer parameterssb-periodicityServingCell a periodicity of a half frames for receptionof a full set of SS/PBCH blocks (SSBs) of the serving cell. If the UE isnot configured a periodicity of the half frames for receptions of theset of SS/PBCH blocks, the UE assumes a periodicity of the half frame onwhich a SSB set is carried. A UE assumes that the periodicity is samefor all SS/PBCH block sets in the serving cell.

For initial cell selection, a UE may assume that half frames withSS/PBCH block sets occur with a periodicity of 2 frames, i.e. 20 ms.

The ssb-PeriodicityServingCell can be 5 ms, 10 ms, 20 ms, 40 ms, 80 ms,or 160 ms, which may be signaled in the IE ServingCellConfigCommon withwhich the network provides this information in dedicated signalling whenconfiguring a UE with a SCells or with an additional cell group (SCG).It also provides it for SpecialCells (SpCells) in Master Cell Group(MCG) and SCG upon reconfiguration with sync.

It is also included in ServingCellConfigCommonSIB IE which is used toconfigure cell specific parameters of a UE's serving cell in SIB1.

-- ASN1START -- TAG-SERVINGCELLCONFIGCOMMONSIB-STARTServingCellConfigCommonSIB ::= SEQUENCE { dowlinkConfigCommonDownlinkConfigCommonSIB, uplinkConfigCommon UplinkConfigCommonSIBOPTIONAL,  -- Need R supplementaryUplink UplinkConfigCommonSIBOPTIONAL,  -- Need R n-TimingAdvanceOffset ENUMERATED { n0, n25560,n39936 } OPTIONAL,  -- Need S ssb-PositionsInBurst SEQUENCE { inOneGroupBIT STRING (SIZE (8)), groupPresence BIT STRING (SIZE (8)) OPTIONAL --Cond Above6GHzOnly }, ssb-PeriodicityServingCell ENUMERATED {ms5, ms10,ms20, ms40, ms80, ms160}, tdd-UL-DL-ConfigurationCommonTDD-UL-DL-ConfigCommon OPTIONAL, -- Cond TDD ss-PBCH-BlockPower INTEGER(−60..50), ... } -- TAG-SERVINGCELLCONFIGCOMMONSIB-STOP -- ASN1STOP

There currently exist certain challenge(s). The SSB/RMSI periodicityassumed by the MTs for initial access and measurement may be differentfrom the SSB/RMSI periodicity assumed by Rel-15 UEs, and methods on thedetermination of the SSB/RMSI periodicity are required.

SUMMARY

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges. Specifically, thisdisclosure provides methods on the determination of the periodicity ofsystem information for the initial access and/or measurement of an IABnode.

There are, proposed herein, various embodiments which address one ormore of the issues disclosed herein.

According to an aspect of the embodiments of the disclosure, a methodperformed at an IAB node is introduced. During the IAB node gets initialaccess to a first parent IAB node, wherein the IAB node firstly join anIAB backhaul link, the IAB node first assumes a predetermined SSBtransmission periodicity, and then searches an SSB at the predeterminedSSB transmission periodicity. Then, the IAB node completes its initialaccess to the first parent IAB node.

According to another aspect of the embodiments of the disclosure, amethod performed at an IAB node is introduced. During the IAB node getsinitial access to a parent IAB node, it first determines itsavailability of SSB transmission periodicity. If there's no informationon actual SSB transmission periodicity in the IAB node, it assumes adefault SSB transmission periodicity, and then searches an SSB at thedefault SSB transmission periodicity. If an actual SSB transmissionperiodicity is available in the IAB node, it searches an SSB at theactual SSB transmission periodicity.

According to another aspect of the embodiments of the disclosure, a basestation performed by an IAB node is introduced. It comprises aprocessing circuitry configured to perform the steps introduced in thedisclosure.

Certain embodiments may provide one or more of the following technicaladvantage(s).

Thus, the disclosure provides methods on the determination of the systeminformation, especially the Synchronization Signals and PhysicalBroadcast Channel (SSB) periodicity and/or Remaining Minimum SystemInformation (RMSI) periodicity for the initial access and/or measurementof an IAB node.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a multi-hop deployment in an integrated access andbackhaul (IAB) network.

FIG. 2 is a reference diagram for IAB-architectures in standalone mode.

FIG. 3 depicts a method in accordance with a first group of embodiments.

FIG. 4 depicts a method in accordance with a second group ofembodiments.

FIG. 5 depicts a method in accordance with a third group of embodiments.

FIG. 6 depicts a method in accordance with a fourth group ofembodiments.

FIG. 7 illustrates a wireless network in which the methods may be used.

FIG. 8 illustrates a User Equipment in accordance with some embodiments.

FIG. 9 illustrates a virtualization environment in which functionsimplemented by some embodiments may be virtualized.

FIG. 10 illustrates a telecommunications network connected via anintermediate network to a host computer in accordance with someembodiments.

FIG. 11 illustrates a host computer communicating via a base stationwith a user equipment over a partially wireless connection in accordancewith some embodiments.

FIG. 12 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments.

FIG. 13 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments.

FIG. 14 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments.

FIG. 15 illustrates methods implemented in a communication systemincluding a host computer, a base station and a user equipment inaccordance with some embodiments.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art.

Some embodiments and groups of embodiments are provided in thisinvention for the determination of the periodicity of system informationfor IAB node for initial access and/or measurement.

The methods described below are separately useable when the MT function,in a base station that is acting as an IAB node, establishes a wirelessbackhaul connection to an existing IAB node. The methods are alsouseable when the MT function, in a base station that is acting as an IABnode, wants to do some measurements on the SSBs. The methods concern howthe base station determines an SSB periodicity and/or RMSI periodicity.FIG. 1 illustrates a network in which such a process may be required.

In the light of an SSB usually contains system information, such as MIBor some other system information in PBCH, and RMSI belongs to systeminformation, the methods described below concern how periodicity ofsystem information is determined for IAB backhaul link. In other words,when MIB periodicity is determined, SSB periodicity is determined as thesame. When the system information is RMSI, RMSI periodicity isdetermined for IAB backhaul link. Also note that some of the embodimentsbelow take the determination of SSB periodicity as example, whiledetermination of RMSI periodicity can follow the similar approacheswhich are not described for simplicity.

The methods described herein are also useable when the MT function in aterminal device, such as a User Equipment, establishes a wirelessbackhaul connection to an existing IAB node, and/or when the MT functionin a terminal device wants to do some measurements on the SSBs. Thus, inthe following description, the term “IAB node” is used to refer to basestation or to terminal device (hereinafter UE as example) when theterminal device having a backhaul connection to an IAB node. Most of thefollowing embodiments take a base station as an example of an IAB nodefor simplicity.

In a first group of embodiments, the periodicity or a defaultperiodicity is predetermined or fixed.

Thus, the base station, and more specifically the MT function whenacting as an IAB node, uses a predetermined or fixed periodicity forSSB, including SSB set transmission and/or SSB measurement. Forsimplicity, a periodicity for SSB set transmission is called SSBtransmission periodicity in this disclosure, not limited to this groupof embodiments.

For example, the base station may be configured such that a 160 msperiodicity, which is the same as the RMSI TTI (Transmission TimeInterval) in NR release 15, is always assumed no matter whichperiodicity of SSB for UE is signalled. The base station may beconfigured such that any other periodicity is predetermined.

FIG. 3 depicts a method in accordance with the first group ofembodiments. In particular, FIG. 3 shows a method performed by an IABnode for determining a periodicity of a SSB for use in an IAB backhaullink. Specifically, in step 302, the IAB node uses a predeterminedperiodicity value as the SSB transmission periodicity at stage 1 or SSBmeasurement periodicity at stage 2.

In another example, periodicity for the RMSI of the base station may beconfigured in a similar way, that is to say, a predetermined or fixedperiodicity.

In the circumstance that the periodicity for the SSB and the RMSI areboth configured a fixed length, the periodicity for the SSB and theperiodicity for the RMSI can be a same or different length. Preferably,transmission of the RMSI is less frequent than transmission of the SSB.

In a second group of embodiments, the periodicity SSB is associated toother parameters.

Thus, the base station, and more specifically the MT function whenacting as an IAB node, uses a periodicity value for the SSB in which MIBis contained that is determined based on some other factor or parameter.

One example is that the periodicity is associated to the frequency bandapplied.

For example, 2 values can be set respectively for low band (band lowerthan e.g. 6 GHz) and high band (band higher than e.g. 6 GHz) as is shownin below table.

SSB periodicity Frequency range of a band in operation for IAB node lowband 320 ms high band 160 ms

Another example is that the periodicity is associated to the SSBperiodicity for UE signalled in UE SIB1. A UE SIB1 refers to a SIB1message broadcasted by a base station for all the UEs in a cell.

One possibility is that the periodicity value is set to be equal to theSSB transmission and/or measurement periodicity value signalled for useby a UE.

Another possibility is to set a minimum periodicity value, and (i) toset the periodicity value to be equal to the SSB periodicity valuesignaled for use by a UE when the periodicity value signaled for use bya UE is greater than the minimum periodicity value, and (ii) to set theperiodicity value to be equal to the minimum periodicity value when theperiodicity value signaled for use by a UE is less than the minimumperiodicity value.

As an example, a minimum value of 20 ms may be set, and then, if the SSBperiodicity for UE is not less than 20 ms, they can be the same;otherwise, 20 ms periodicity is assumed.

SSB periodicity SSB periodicity for UE P0 for IAB P1 P0 >= 20 ms P1 = P0P0 < 20 ms 20 ms

FIG. 4 depicts a method in accordance with the second group ofembodiments. In particular, FIG. 4 shows a method performed by an IABnode for determining a periodicity of SSB transmission and/ormeasurement for use in an IAB backhaul link. Specifically, in step 402,the IAB node determines a periodicity value based on at least onedifferent parameter. In the second group of embodiments, periodicity fortransmission of the RMSI for use in an IAB backhaul link can bedetermined in the similar way as illustrated above. In the followingembodiments, determination of RMSI periodicity for an IAB node forinitial access or measurement will not be illustrated separately fromdetermination of SSB periodicity for an IAB node for simplicity, whilethe determination of RMSI periodicity might be executed separately fromthe determination of SSB periodicity, for example, by followingdifferent groups of embodiments or different examples in a same group ofembodiments.

In a third group of embodiments, the periodicity of SSB set and/or RMSItransmission and/or measurement can be signalled, e.g. via UE SIB1 or UEMIB, and/or via a newly defined IAB SIB or IAB MIB, and a default SSBand/or RMSI periodicity can be assumed for initial access before actualindicated SSB and/or RMSI is available.

A UE MIB refers to a master information block (MIB) broadcasted in a UESSB from a base station for all the UEs in a cell. An IAB SIB may refersto a message sent from an IAB node as parent node for all the othernodes that can establish an IAB backhaul link with it. An IAB MIB mayrefers to a message sent in an IAB SSB from an IAB node as parent nodefor all the other nodes that can establish an IAB backhaul link with it.

Thus, the base station, and more specifically the MT function whenacting as an IAB node, uses a periodicity for SSB set and/or the RMSItransmission and/or measurement that is signalled to it. The value maybe signalled by the parent node, that is the IAB donor, or the other IABnode with which the base station wishes to establish an IAB backhaullink.

For example, a default periodicity can be 160 ms and a parameter“IABssb-PeriodicityServingCell” can be included as shown below:

-- ASN1START -- TAG-SERVINGCELLCONFIGCOMMONSIB-STARTServingCellConfigCommonSIB ::= SEQUENCE { dowlinkConfigCommonDownlinkConfigCommonSIB, uplinkConfigCommon UplinkConfigCommonSIBOPTIONAL,  -- Need R supplementaryUplink UplinkConfigCommonSIBOPTIONAL,  -- Need R n-TimingAdvanceOffset ENUMERATED { n0, n25560,n39936 } OPTIONAL,  -- Need S ssb-PositionsInBurst SEQUENCE { inOneGroupBIT STRING (SIZE (8)), groupPresence BIT STRING (SIZE (8)) OPTIONAL --Cond Above6GHzOnly }, ssb-PeriodicityServingCell ENUMERATED {ms5, ms10,ms20, ms40, ms80, ms160}, IABssb-PeriodicityServingCell ENUMERATED{ms10, ms40, ms80, ms160, ms320, ms480}, tdd-UL-DL-ConfigurationCommonTDD-UL-DL-ConfigCommon OPTIONAL, -- Cond TDD ss-PBCH-BlockPower INTEGER(−60..50), ... } -- TAG-SERVINGCELLCONFIGCOMMONSIB-STOP -- ASN1STOP

FIG. 5 depicts a method in accordance with the third group ofembodiments. In particular, FIG. 5 shows a method performed by an IABnode for determining a periodicity of of SSB set and/or RMSItransmission and/or measurement for use in an IAB backhaul link. Asmentioned above, the SSB set for use in an IAB backhaul link canspecifically be used for IAB backhaul link, or it can also be a same setof SSBs used for access UEs. Specifically, FIG. 5 shows a methodbeginning at step 502, in which the IAB node receives a signalingmessage indicating a periodicity value. Then, in step 504, the IAB nodeuses the indicated periodicity value for joining IAB backhaul link.

In accordance with the third group of embodiments, a process is alsoperformed in the base station acting as the parent node. Specifically,said base station performs a method comprising signaling a periodicityof transmission of SSB and/or RMSI for use by an IAB node in an IABbackhaul link with said base station.

The periodicity may be included as a parameter in a UE SIB1 and/or IABSIB transmitted from the base station. Alternatively, the periodicitymay be included as a parameter in a UE MIB and/or IAB MIB transmittedfrom the base station. A first indicated periodicity value may besignalled for the SSB and a second indicated periodicity value may besignalled for the RMSI. In that case, the first indicated periodicityvalue may be different from the second indicated periodicity value.

Different periodicity values may be indicated for different processes.In that case, the processes may be selected from: IAB node initialaccess, IAB node detection, and IAB node measurement.

In a fourth group of embodiments one periodicity can be assumed andrandomly selected from a set of candidates by the receiver (child IABnode) itself.

Thus, the base station, and more specifically the MT function whenacting as an IAB node, uses a selected periodicity for the SSB and/orthe RMSI, where the periodicity is selected value from a plurality ofpredetermined permitted periodicity values. For example, the periodicitymay be randomly selected from the plurality of permitted periodicityvalues. The base station may be configured with the plurality ofpermitted periodicity values, which form a candidate set. For example,the set of candidates may be 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160ms, or may include or comprise some of those values.

A periodicity may be chosen and used on any subsequent occasions, or anew periodicity value may be selected whenever a periodicity is needed.

FIG. 6 depicts a method in accordance with the fourth group ofembodiments. In particular, FIG. 6 shows a method performed by an IABnode for determining a periodicity of a SSB and/or a RMSI for use in anIAB backhaul link. Specifically, in step 602, the IAB node selects aperiodicity value from a plurality of permitted periodicity values.

In any of the groups of embodiments described above, the SSB periodicityand the RMSI periodicity can be either the same or different.Specifically, the SSB periodicity may be determined by a method inaccordance with one group of embodiments, while the RMSI periodicity isdetermined by a method in accordance with a different group ofembodiments.

Alternatively, the SSB periodicity and the RMSI periodicity may bedetermined by methods in accordance with the same group of embodiments,but in a way that may produce different results. For example, in thefirst group of embodiments, different predetermined or fixedperiodicities may be used for the SSB periodicity and the RMSIperiodicity. In the second group of embodiments, different parametersmay be used for determining the SSB periodicity and the RMSIperiodicity. In the third group of embodiments, different values of theSSB periodicity and the RMSI periodicity may be signalled. In the fourthgroup of embodiments, the IAB node may select different values for theSSB periodicity and the RMSI periodicity from the plurality of permittedperiodicity values. Thus, there may be separate signalling and/orassumptions applied for the SSB periodicity and the RMSI periodicity forthe IAB node.

In any of the groups of embodiments described above, different orseparate SSB periodicities may be determined for the purpose ofdifferent processes performed by the IAB node, such as IAB node initialaccess, IAB node detection and IAB node measurement. At least one ofthese different periodicities may be determined by means of a method inaccordance with any of the groups of embodiments, i.e. by using apredetermined periodicity value; determining a periodicity value basedon at least one different parameter; receiving a signaling messageindicating a periodicity value and using the periodicity value from aplurality of permitted periodicity values.

For example, different periodicity values may be used for IAB nodeinitial access and for IAB node detection. As another example, differentperiodicity values may be used for IAB node measurement and for IAB nodeinitial access. As another example, different periodicity values may beused for IAB node detection and for IAB node measurement.

As mentioned above, any of the methods described above may be performedby a Mobile Termination function of a base station acting as an IABnode. As another example, any of the methods described above may beperformed by a Mobile Termination function of a User Equipment.

Below are some embodiments listed for further illustrating the inventionwhile the idea of the invention is not limited to those listedembodiments.

-   -   1. A method performed by an IAB node for determining a        periodicity of a SSB and/or a RMSI for use in an IAB backhaul        link, the method comprising:        -   using a predetermined periodicity value.    -   2. The method of embodiment 1, comprising using the        predetermined periodicity value even when it differs from a        periodicity signaled for use by a UE.    -   3. The method of embodiment 1 or 2, comprising using a first        predetermined periodicity value for the SSB and using a second        predetermined periodicity value for the RMSI.    -   4. The method of embodiment 3, wherein the first predetermined        periodicity value is different from the second predetermined        periodicity value.    -   5. The method of any of embodiments 1-4, comprising using        different predetermined periodicity values for different        processes.    -   6. The method of embodiment 5, wherein the processes are        selected from: IAB node initial access, IAB node detection, and        IAB node measurement.    -   7. The method of any of embodiments 1-6, comprising determining        the periodicity of the SSB and/or the RMSI for use in an IAB        backhaul link when the IAB node establishes a wireless backhaul        connection to an existing IAB node.    -   8. The method of any of embodiments 1-6, comprising determining        the periodicity of the SSB when the IAB node wishes to perform        measurements on SSBs.    -   9. The method of embodiment 8, wherein the determined        periodicity of the SSB is part of the SSB based RRM measurement        Timing Configuration, SMTC.    -   10. A method performed by an IAB node for determining a        periodicity of a SSB and/or a RMSI for use in an IAB backhaul        link, the method comprising:        -   determining a periodicity value based on at least one            different parameter.    -   11. The method of embodiment 10, comprising determining the        periodicity value based on a frequency band being used for the        IAB backhaul link.    -   12. The method of embodiment 10 or 11, comprising determining        the periodicity value based on a SSB periodicity value signaled        for use by a UE.    -   13. The method of embodiment 12, comprising setting the        periodicity value to be equal to the SSB periodicity value        signaled for use by a UE.    -   14. The method of embodiment 13, comprising setting a minimum        periodicity value, and (i) setting the periodicity value to be        equal to the SSB periodicity value signaled for use by a UE when        the periodicity value signaled for use by a UE is not less than        the minimum periodicity value, and (ii) setting the periodicity        value to be equal to the minimum periodicity value when the        periodicity value signaled for use by a UE is less than the        minimum periodicity value.    -   15. The method of one of embodiments 10 to 14, comprising using        a first determined periodicity value for the SSB and using a        second determined periodicity value for the RMSI.    -   16. The method of embodiment 15, wherein the first determined        periodicity value is different from the second predetermined        periodicity value.    -   17. The method of any of embodiments 10-16, comprising using        different determined periodicity values for different processes.    -   18. The method of embodiment 17, wherein the processes are        selected from: IAB node initial access, IAB node detection, and        IAB node measurement.    -   19. The method of any of embodiments 10-18, comprising        determining the periodicity of the SSB and/or the RMSI for use        in an IAB backhaul link when the IAB node establishes a wireless        backhaul connection to an existing IAB node.    -   20. The method of any of embodiments 10-18, comprising        determining the periodicity of the SSB when the IAB node wishes        to perform measurements on SSBs.    -   21. The method of embodiment 20, wherein the determined        periodicity of the SSB is part of the SSB based RRM measurement        Timing Configuration, SMTC.    -   22. A method performed by an IAB node for determining a        periodicity of a SSB and/or a RMSI for use in an IAB backhaul        link, the method comprising:        -   receiving a signaling message indicating a periodicity            value; and        -   using the indicated periodicity value for the IAB backhaul            link.    -   23. The method of embodiment 22, comprising receiving the        signaling message from a second IAB node with which said IAB        node wishes to establish the IAB backhaul link.    -   24. The method of embodiment 23, wherein the periodicity value        is included as a parameter in a UE SIB1 and/or IAB SIB        transmitted from the second IAB node.    -   25. The method of embodiment 23, wherein the periodicity value        is included as a parameter in a UE MIB and/or IAB MIB        transmitted from the second IAB node.    -   26. The method of one of embodiments 22-25, comprising using a        default periodicity value before receiving said signaling        message.    -   27. The method of one of embodiments 22-26, comprising using a        first indicated periodicity value for the SSB and using a second        indicated periodicity value for the RMSI.    -   28. The method of embodiment 27, wherein the first indicated        periodicity value is different from the second indicated        periodicity value.    -   29. The method of any of embodiments 22-28, comprising using        different indicated periodicity values for different processes.    -   30. The method of embodiment 29, wherein the processes are        selected from: IAB node initial access, IAB node detection, and        IAB node measurement.    -   31. The method of any of embodiments 22-30, comprising        determining the periodicity of the SSB and/or the RMSI for use        in an IAB backhaul link when the IAB node establishes a wireless        backhaul connection to an existing IAB node.    -   32. The method of any of embodiments 22-30, comprising        determining the periodicity of the SSB when the IAB node wishes        to perform measurements on SSBs.    -   33. The method of embodiment 32, wherein the determined        periodicity of the SSB is part of the SSB based RRM measurement        Timing Configuration, SMTC.    -   34. A method performed by an IAB node for determining a        periodicity of a SSB and/or a RMSI for use in an IAB backhaul        link, the method comprising:        -   selecting a periodicity value from a plurality of permitted            periodicity values.    -   35. The method of embodiment 34, comprising randomly selecting        the periodicity value from the plurality of permitted        periodicity values.    -   36. The method of embodiment 34 or 35, comprising using a first        selected periodicity value for the SSB and using a second        selected periodicity value for the RMSI.    -   37. The method of embodiment 36, wherein the first selected        periodicity value is different from the second selected        periodicity value.    -   38. The method of any of embodiments 34-37, comprising using        different selected periodicity values for different processes.    -   39. The method of embodiment 38, wherein the processes are        selected from: IAB node initial access, IAB node detection, and        IAB node measurement.    -   40. The method of any of embodiments 34-39, comprising        determining the periodicity of the SSB and/or the RMSI for use        in an IAB backhaul link when the IAB node establishes a wireless        backhaul connection to an existing IAB node.    -   41. The method of any of embodiments 34-39, comprising        determining the periodicity of the SSB when the IAB node wishes        to perform measurements on SSBs.    -   42. The method of embodiment 41, wherein the determined        periodicity of the SSB is part of the SSB based RRM measurement        Timing Configuration, SMTC.    -   43. A method performed by an IAB node for determining a        periodicity of a SSB and a RMSI for use in an IAB backhaul link,        wherein the periodicity of the SSB and the periodicity of the        RMSI may be the same or different.    -   44. A method performed by an IAB node for determining a        periodicity of a SSB and a RMSI for use in an IAB backhaul link,        wherein the periodicity of the SSB and the periodicity of the        RMSI are different.    -   45. A method performed by an IAB node for determining a        periodicity of a SSB and a RMSI for use in an IAB backhaul link,        comprising determining the periodicity of the SSB by means of a        first method and determining the periodicity of the RMSI by        means of a different method.    -   46. The method of embodiment 45, wherein at least one of the        first method and the second method are selected from:        -   using a predetermined periodicity value;        -   determining a periodicity value based on at least one            different parameter.        -   receiving a signaling message indicating a periodicity value            and using the indicated periodicity value for the IAB            backhaul link; and        -   selecting a periodicity value from a plurality of permitted            periodicity values.    -   47. A method performed by an IAB node for determining a        periodicity of a SSB for use in an IAB backhaul link, the method        comprising:        -   using separately determined periodicity values for different            processes.    -   48. The method of embodiment 47, wherein the processes are        selected from: IAB node initial access, IAB node detection, and        IAB node measurement.    -   49. The method of embodiment 47 or 48, wherein at least one of        the periodicity values are determined by:        -   using a predetermined periodicity value;        -   determining a periodicity value based on at least one            different parameter.        -   receiving a signaling message indicating a periodicity value            and using the indicated periodicity value for the IAB            backhaul link; and        -   selecting a periodicity value from a plurality of permitted            periodicity values.    -   50. The method of one of embodiments 47-49, comprising using        different periodicity values for IAB node initial access and for        IAB node detection, and/or using different periodicity values        for IAB node measurement and for IAB node initial access, and/or        using different periodicity values for IAB node detection and        for IAB node measurement.    -   51. The method of any preceding embodiment, performed by a        Mobile Termination function of a base station acting as an IAB        node.    -   52. A method performed by a base station acting as an IAB node,        the method comprising signaling a periodicity of a SSB and/or a        RMSI for use by an IAB node in an IAB backhaul link with said        base station.    -   53. The method of embodiment 52, comprising including the        periodicity as a parameter in a UE SIB1 and/or IAB SIB        transmitted from the base station.    -   54. The method of embodiment 52, comprising including the        periodicity as a parameter in a UE MIB and/or IAB MIB        transmitted from the base station.    -   55. The method of one of embodiments 52-54, comprising using a        first indicated periodicity value for the SSB and using a second        indicated periodicity value for the RMSI.    -   56. The method of embodiment 55, wherein the first indicated        periodicity value is different from the second indicated        periodicity value.    -   57. The method of any of embodiments 52-56, comprising using        different indicated periodicity values for different processes.    -   58. The method of embodiment 57, wherein the processes are        selected from: IAB node initial access, IAB node detection, and        IAB node measurement.    -   59. The method of any of the previous embodiments, further        comprising:        -   obtaining user data; and        -   forwarding the user data to a host computer or a wireless            device.    -   60. A base station for use as an IAB node, the base station        comprising:        -   processing circuitry configured to perform any of the steps            of any of embodiments 1-59;        -   power supply circuitry configured to supply power to the            base station.    -   61. A communication system including a host computer comprising:        -   processing circuitry configured to provide user data; and        -   a communication interface configured to forward the user            data to a cellular network for transmission to a user            equipment (UE),        -   wherein the cellular network comprises a base station having            a radio interface and processing circuitry, the base            station's processing circuitry configured to perform any of            the steps of any of embodiments 1-59.    -   62. The communication system of embodiment 61 further including        the base station.    -   63. The communication system of embodiment 61 or 62 further        including the UE, wherein the UE is configured to communicate        with the base station.    -   64. The communication system of embodiments 61-63, wherein:        -   the processing circuitry of the host computer is configured            to execute a host application, thereby providing the user            data; and        -   the UE comprises processing circuitry configured to execute            a client application associated with the host application.    -   65. A method implemented in a communication system including a        host computer, a base station and a user equipment (UE), the        method comprising:        -   at the host computer, providing user data; and        -   at the host computer, initiating a transmission carrying the            user data to the UE via a cellular network comprising the            base station, wherein the base station performs any of the            steps of any of embodiments 1-59.    -   66. The method of embodiment 65, further comprising, at the base        station, transmitting the user data.    -   67. The method of embodiments 65-66, wherein the user data is        provided at the host computer by executing a host application,        the method further comprising, at the UE, executing a client        application associated with the host application.    -   68. The method of embodiments 65-67, wherein the base station        performs said steps in a MT function.    -   69. A user equipment (UE) configured to communicate with a base        station, the UE comprising a radio interface and processing        circuitry configured to performs the steps of embodiments 65-68.    -   70. A communication system including a host computer comprising        a communication interface configured to receive user data        originating from a transmission from a user equipment (UE) to a        base station, wherein the base station comprises a radio        interface and processing circuitry, the base station's        processing circuitry configured to perform any of the steps of        any of embodiments 1-59.    -   71. The communication system of embodiment 70 further including        the base station.    -   72. The communication system of embodiments 70-71, further        including the UE, wherein the UE is configured to communicate        with the base station.    -   73. The communication system of embodiments 70-72, wherein:        -   the processing circuitry of the host computer is configured            to execute a host application;        -   the UE is configured to execute a client application            associated with the host application, thereby providing the            user data to be received by the host computer.

Although the subject matter described herein may be implemented in anyappropriate type of system using any suitable components, theembodiments disclosed herein are described in relation to a wirelessnetwork, such as the example wireless network illustrated in FIG. 7 .For simplicity, the wireless network of FIG. 7 only depicts networkQQ106, network nodes QQ160 and QQ160 b, and WDs QQ110, QQ110 b, andQQ110 c. In practice, a wireless network may further include anyadditional elements suitable to support communication between wirelessdevices or between a wireless device and another communication device,such as a landline telephone, a service provider, or any other networknode or end device. Of the illustrated components, network node QQ160and wireless device (WD) QQ110 are depicted with additional detail. Thewireless network may provide communication and other types of servicesto one or more wireless devices to facilitate the wireless devices'access to and/or use of the services provided by, or via, the wirelessnetwork.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network QQ106 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node QQ160 and WD QQ110 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 7 , network node QQ160 includes processing circuitry QQ170,device readable medium QQ180, interface QQ190, auxiliary equipmentQQ184, power source QQ186, power circuitry QQ187, and antenna QQ162.Although network node QQ160 illustrated in the example wireless networkof FIG. 7 may represent a device that includes the illustratedcombination of hardware components, other embodiments may comprisenetwork nodes with different combinations of components. It is to beunderstood that a network node comprises any suitable combination ofhardware and/or software needed to perform the tasks, features,functions and methods disclosed herein. Moreover, while the componentsof network node QQ160 are depicted as single boxes located within alarger box, or nested within multiple boxes, in practice, a network nodemay comprise multiple different physical components that make up asingle illustrated component (e.g., device readable medium QQ180 maycomprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node QQ160comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeB's.In such a scenario, each unique NodeB and RNC pair, may in someinstances be considered a single separate network node. In someembodiments, network node QQ160 may be configured to support multipleradio access technologies (RATs). In such embodiments, some componentsmay be duplicated (e.g., separate device readable medium QQ180 for thedifferent RATs) and some components may be reused (e.g., the sameantenna QQ162 may be shared by the RATs). Network node QQ160 may alsoinclude multiple sets of the various illustrated components fordifferent wireless technologies integrated into network node QQ160, suchas, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wirelesstechnologies. These wireless technologies may be integrated into thesame or different chip or set of chips and other components withinnetwork node QQ160.

Processing circuitry QQ170 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry QQ170 may include processinginformation obtained by processing circuitry QQ170 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedin the network node, and/or performing one or more operations based onthe obtained information or converted information, and as a result ofsaid processing making a determination.

Processing circuitry QQ170 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode QQ160 components, such as device readable medium QQ180, networknode QQ160 functionality. For example, processing circuitry QQ170 mayexecute instructions stored in device readable medium QQ180 or in memorywithin processing circuitry QQ170. Such functionality may includeproviding any of the various wireless features, functions, or benefitsdiscussed herein. In some embodiments, processing circuitry QQ170 mayinclude a system on a chip (SOC).

In some embodiments, processing circuitry QQ170 may include one or moreof radio frequency (RF) transceiver circuitry QQ172 and basebandprocessing circuitry QQ174. In some embodiments, radio frequency (RF)transceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on separate chips (or sets of chips), boards, or units, such as radiounits and digital units. In alternative embodiments, part or all of RFtransceiver circuitry QQ172 and baseband processing circuitry QQ174 maybe on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry QQ170executing instructions stored on device readable medium QQ180 or memorywithin processing circuitry QQ170. In alternative embodiments, some orall of the functionality may be provided by processing circuitry QQ170without executing instructions stored on a separate or discrete devicereadable medium, such as in a hard-wired manner. In any of thoseembodiments, whether executing instructions stored on a device readablestorage medium or not, processing circuitry QQ170 can be configured toperform the described functionality. The benefits provided by suchfunctionality are not limited to processing circuitry QQ170 alone or toother components of network node QQ160, but are enjoyed by network nodeQQ160 as a whole, and/or by end users and the wireless networkgenerally.

Device readable medium QQ180 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry QQ170. Device readable medium QQ180 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ170 and, utilized by network node QQ160.Device readable medium QQ180 may be used to store any calculations madeby processing circuitry QQ170 and/or any data received via interfaceQQ190. In some embodiments, processing circuitry QQ170 and devicereadable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication ofsignalling and/or data between network node QQ160, network QQ106, and/orWDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s)QQ194 to send and receive data, for example to and from network QQ106over a wired connection. Interface QQ190 also includes radio front endcircuitry QQ192 that may be coupled to, or in certain embodiments a partof, antenna QQ162. Radio front end circuitry QQ192 comprises filtersQQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may beconnected to antenna QQ162 and processing circuitry QQ170. Radio frontend circuitry may be configured to condition signals communicatedbetween antenna QQ162 and processing circuitry QQ170. Radio front endcircuitry QQ192 may receive digital data that is to be sent out to othernetwork nodes or WDs via a wireless connection. Radio front endcircuitry QQ192 may convert the digital data into a radio signal havingthe appropriate channel and bandwidth parameters using a combination offilters QQ198 and/or amplifiers QQ196. The radio signal may then betransmitted via antenna QQ162. Similarly, when receiving data, antennaQQ162 may collect radio signals which are then converted into digitaldata by radio front end circuitry QQ192. The digital data may be passedto processing circuitry QQ170. In other embodiments, the interface maycomprise different components and/or different combinations ofcomponents.

In certain alternative embodiments, network node QQ160 may not includeseparate radio front end circuitry QQ192, instead, processing circuitryQQ170 may comprise radio front end circuitry and may be connected toantenna QQ162 without separate radio front end circuitry QQ192.Similarly, in some embodiments, all or some of RF transceiver circuitryQQ172 may be considered a part of interface QQ190. In still otherembodiments, interface QQ190 may include one or more ports or terminalsQQ194, radio front end circuitry QQ192, and RF transceiver circuitryQQ172, as part of a radio unit (not shown), and interface QQ190 maycommunicate with baseband processing circuitry QQ174, which is part of adigital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna QQ162 may becoupled to radio front end circuitry QQ190 and may be any type ofantenna capable of transmitting and receiving data and/or signalswirelessly. In some embodiments, antenna QQ162 may comprise one or moreomni-directional, sector or panel antennas operable to transmit/receiveradio signals between, for example, 2 GHz and 66 GHz. Anomni-directional antenna may be used to transmit/receive radio signalsin any direction, a sector antenna may be used to transmit/receive radiosignals from devices within a particular area, and a panel antenna maybe a line of sight antenna used to transmit/receive radio signals in arelatively straight line. In some instances, the use of more than oneantenna may be referred to as MIMO. In certain embodiments, antennaQQ162 may be separate from network node QQ160 and may be connectable tonetwork node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry QQ187 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network nodeQQ160 with power for performing the functionality described herein.Power circuitry QQ187 may receive power from power source QQ186. Powersource QQ186 and/or power circuitry QQ187 may be configured to providepower to the various components of network node QQ160 in a form suitablefor the respective components (e.g., at a voltage and current levelneeded for each respective component). Power source QQ186 may either beincluded in, or external to, power circuitry QQ187 and/or network nodeQQ160. For example, network node QQ160 may be connectable to an externalpower source (e.g., an electricity outlet) via an input circuitry orinterface such as an electrical cable, whereby the external power sourcesupplies power to power circuitry QQ187. As a further example, powersource QQ186 may comprise a source of power in the form of a battery orbattery pack which is connected to, or integrated in, power circuitryQQ187. The battery may provide backup power should the external powersource fail. Other types of power sources, such as photovoltaic devices,may also be used.

Alternative embodiments of network node QQ160 may include additionalcomponents beyond those shown in FIG. 7 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node QQ160 may include user interface equipment to allow inputof information into network node QQ160 and to allow output ofinformation from network node QQ160. This may allow a user to performdiagnostic, maintenance, repair, and other administrative functions fornetwork node QQ160.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE).Communicating wirelessly may involve transmitting and/or receivingwireless signals using electromagnetic waves, radio waves, infraredwaves, and/or other types of signals suitable for conveying informationthrough air. In some embodiments, a WD may be configured to transmitand/or receive information without direct human interaction. Forinstance, a WD may be designed to transmit information to a network on apredetermined schedule, when triggered by an internal or external event,or in response to requests from the network. Examples of a WD include,but are not limited to, a smart phone, a mobile phone, a cell phone, avoice over IP (VoIP) phone, a wireless local loop phone, a desktopcomputer, a personal digital assistant (PDA), a wireless cameras, agaming console or device, a music storage device, a playback appliance,a wearable terminal device, a wireless endpoint, a mobile station, atablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mountedequipment (LME), a smart device, a wireless customer-premise equipment(CPE). a vehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device. As yet anotherspecific example, in an Internet of Things (IoT) scenario, a WD mayrepresent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a machine-to-machine (M2M) device, which may in a 3GPP contextbe referred to as an MTC device. As one particular example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Particular examples of such machines or devices are sensors,metering devices such as power meters, industrial machinery, or home orpersonal appliances (e.g. refrigerators, televisions, etc.) personalwearables (e.g., watches, fitness trackers, etc.). In other scenarios, aWD may represent a vehicle or other equipment that is capable ofmonitoring and/or reporting on its operational status or other functionsassociated with its operation. A WD as described above may represent theendpoint of a wireless connection, in which case the device may bereferred to as a wireless terminal. Furthermore, a WD as described abovemay be mobile, in which case it may also be referred to as a mobiledevice or a mobile terminal.

As illustrated, wireless device QQ110 includes antenna QQ111, interfaceQQ114, processing circuitry QQ120, device readable medium QQ130, userinterface equipment QQ132, auxiliary equipment QQ134, power source QQ136and power circuitry QQ137. WD QQ110 may include multiple sets of one ormore of the illustrated components for different wireless technologiessupported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi,WiMAX, or Bluetooth wireless technologies, just to mention a few. Thesewireless technologies may be integrated into the same or different chipsor set of chips as other components within WD QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface QQ114. In certain alternative embodiments, antenna QQ111 maybe separate from WD QQ110 and be connectable to WD QQ110 through aninterface or port. Antenna QQ111, interface QQ114, and/or processingcircuitry QQ120 may be configured to perform any receiving ortransmitting operations described herein as being performed by a WD. Anyinformation, data and/or signals may be received from a network nodeand/or another WD. In some embodiments, radio front end circuitry and/orantenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitryQQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one ormore filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114is connected to antenna QQ111 and processing circuitry QQ120, and isconfigured to condition signals communicated between antenna QQ111 andprocessing circuitry QQ120. Radio front end circuitry QQ112 may becoupled to or a part of antenna QQ111. In some embodiments, WD QQ110 maynot include separate radio front end circuitry QQ112; rather, processingcircuitry QQ120 may comprise radio front end circuitry and may beconnected to antenna QQ111. Similarly, in some embodiments, some or allof RF transceiver circuitry QQ122 may be considered a part of interfaceQQ114. Radio front end circuitry QQ112 may receive digital data that isto be sent out to other network nodes or WDs via a wireless connection.Radio front end circuitry QQ112 may convert the digital data into aradio signal having the appropriate channel and bandwidth parametersusing a combination of filters QQ118 and/or amplifiers QQ116. The radiosignal may then be transmitted via antenna QQ111. Similarly, whenreceiving data, antenna QQ111 may collect radio signals which are thenconverted into digital data by radio front end circuitry QQ112. Thedigital data may be passed to processing circuitry QQ120. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

Processing circuitry QQ120 may comprise a combination of one or more ofa microprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD QQ110components, such as device readable medium QQ130, WD QQ110functionality. Such functionality may include providing any of thevarious wireless features or benefits discussed herein. For example,processing circuitry QQ120 may execute instructions stored in devicereadable medium QQ130 or in memory within processing circuitry QQ120 toprovide the functionality disclosed herein.

As illustrated, processing circuitry QQ120 includes one or more of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitryQQ120 of WD QQ110 may comprise a SOC. In some embodiments, RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be on separate chips or setsof chips. In alternative embodiments, part or all of baseband processingcircuitry QQ124 and application processing circuitry QQ126 may becombined into one chip or set of chips, and RF transceiver circuitryQQ122 may be on a separate chip or set of chips. In still alternativeembodiments, part or all of RF transceiver circuitry QQ122 and basebandprocessing circuitry QQ124 may be on the same chip or set of chips, andapplication processing circuitry QQ126 may be on a separate chip or setof chips. In yet other alternative embodiments, part or all of RFtransceiver circuitry QQ122, baseband processing circuitry QQ124, andapplication processing circuitry QQ126 may be combined in the same chipor set of chips. In some embodiments, RF transceiver circuitry QQ122 maybe a part of interface QQ114. RF transceiver circuitry QQ122 maycondition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality describedherein as being performed by a WD may be provided by processingcircuitry QQ120 executing instructions stored on device readable mediumQQ130, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry QQ120 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry QQ120 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry QQ120 alone or to other componentsof WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end usersand the wireless network generally.

Processing circuitry QQ120 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry QQ120, may include processinginformation obtained by processing circuitry QQ120 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD QQ110, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium QQ130 may be operable to store a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry QQ120. Device readable medium QQ130 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry QQ120. In someembodiments, processing circuitry QQ120 and device readable medium QQ130may be considered to be integrated.

User interface equipment QQ132 may provide components that allow for ahuman user to interact with WD QQ110. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipmentQQ132 may be operable to produce output to the user and to allow theuser to provide input to WD QQ110. The type of interaction may varydepending on the type of user interface equipment QQ132 installed in WDQQ110. For example, if WD QQ110 is a smart phone, the interaction may bevia a touch screen; if WD QQ110 is a smart meter, the interaction may bethrough a screen that provides usage (e.g., the number of gallons used)or a speaker that provides an audible alert (e.g., if smoke isdetected). User interface equipment QQ132 may include input interfaces,devices and circuits, and output interfaces, devices and circuits. Userinterface equipment QQ132 is configured to allow input of informationinto WD QQ110, and is connected to processing circuitry QQ120 to allowprocessing circuitry QQ120 to process the input information. Userinterface equipment QQ132 may include, for example, a microphone, aproximity or other sensor, keys/buttons, a touch display, one or morecameras, a USB port, or other input circuitry. User interface equipmentQQ132 is also configured to allow output of information from WD QQ110,and to allow processing circuitry QQ120 to output information from WDQQ110. User interface equipment QQ132 may include, for example, aspeaker, a display, vibrating circuitry, a USB port, a headphoneinterface, or other output circuitry. Using one or more input and outputinterfaces, devices, and circuits, of user interface equipment QQ132, WDQQ110 may communicate with end users and/or the wireless network, andallow them to benefit from the functionality described herein.

Auxiliary equipment QQ134 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD QQ110 may further comprise power circuitryQQ137 for delivering power from power source QQ136 to the various partsof WD QQ110 which need power from power source QQ136 to carry out anyfunctionality described or indicated herein. Power circuitry QQ137 mayin certain embodiments comprise power management circuitry. Powercircuitry QQ137 may additionally or alternatively be operable to receivepower from an external power source; in which case WD QQ110 may beconnectable to the external power source (such as an electricity outlet)via input circuitry or an interface such as an electrical power cable.Power circuitry QQ137 may also in certain embodiments be operable todeliver power from an external power source to power source QQ136. Thismay be, for example, for the charging of power source QQ136. Powercircuitry QQ137 may perform any formatting, converting, or othermodification to the power from power source QQ136 to make the powersuitable for the respective components of WD QQ110 to which power issupplied.

FIG. 8 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE QQ2200 may be any UE identifiedby the 3^(rd) Generation Partnership Project (3GPP), including a NB-IoTUE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC)UE. UE QQ200, as illustrated in FIG. 8 , is one example of a WDconfigured for communication in accordance with one or morecommunication standards promulgated by the 3^(rd) Generation PartnershipProject (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. Asmentioned previously, the term WD and UE may be used interchangeable.Accordingly, although FIG. 8 is a UE, the components discussed hereinare equally applicable to a WD, and vice-versa.

In FIG. 8 , UE QQ200 includes processing circuitry QQ201 that isoperatively coupled to input/output interface QQ205, radio frequency(RF) interface QQ209, network connection interface QQ211, memory QQ215including random access memory (RAM) QQ217, read-only memory (ROM)QQ219, and storage medium QQ221 or the like, communication subsystemQQ231, power source QQ233, and/or any other component, or anycombination thereof. Storage medium QQ221 includes operating systemQQ223, application program QQ225, and data QQ227. In other embodiments,storage medium QQ221 may include other similar types of information.Certain UEs may utilize all of the components shown in FIG. 8 , or onlya subset of the components. The level of integration between thecomponents may vary from one UE to another UE. Further, certain UEs maycontain multiple instances of a component, such as multiple processors,memories, transceivers, transmitters, receivers, etc.

In FIG. 8 , processing circuitry QQ201 may be configured to processcomputer instructions and data. Processing circuitry QQ201 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry QQ201 may includetwo central processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface QQ205 may beconfigured to provide a communication interface to an input device,output device, or input and output device. UE QQ200 may be configured touse an output device via input/output interface QQ205. An output devicemay use the same type of interface port as an input device. For example,a USB port may be used to provide input to and output from UE QQ200. Theoutput device may be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE QQ200 may be configured to use aninput device via input/output interface QQ205 to allow a user to captureinformation into UE QQ200. The input device may include atouch-sensitive or presence-sensitive display, a camera (e.g., a digitalcamera, a digital video camera, a web camera, etc.), a microphone, asensor, a mouse, a trackball, a directional pad, a trackpad, a scrollwheel, a smartcard, and the like. The presence-sensitive display mayinclude a capacitive or resistive touch sensor to sense input from auser. A sensor may be, for instance, an accelerometer, a gyroscope, atilt sensor, a force sensor, a magnetometer, an optical sensor, aproximity sensor, another like sensor, or any combination thereof. Forexample, the input device may be an accelerometer, a magnetometer, adigital camera, a microphone, and an optical sensor.

In FIG. 8 , RF interface QQ209 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface QQ211 may beconfigured to provide a communication interface to network QQ243 a.Network QQ243 a may encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network QQ243 a may comprise aWi-Fi network. Network connection interface QQ211 may be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface QQ211 may implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions may share circuit components, software or firmware,or alternatively may be implemented separately.

RAM QQ217 may be configured to interface via bus QQ202 to processingcircuitry QQ201 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM QQ219may be configured to provide computer instructions or data to processingcircuitry QQ201. For example, ROM QQ219 may be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage mediumQQ221 may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium QQ221 may be configured toinclude operating system QQ223, application program QQ225 such as a webbrowser application, a widget or gadget engine or another application,and data file QQ227. Storage medium QQ221 may store, for use by UEQQ200, any of a variety of various operating systems or combinations ofoperating systems.

Storage medium QQ221 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium QQ221 may allow UE QQ200 to access computer-executableinstructions, application programs or the like, stored on transitory ornon-transitory memory media, to off-load data, or to upload data. Anarticle of manufacture, such as one utilizing a communication system maybe tangibly embodied in storage medium QQ221, which may comprise adevice readable medium.

In FIG. 8 , processing circuitry QQ201 may be configured to communicatewith network QQ243 b using communication subsystem QQ231. Network QQ243a and network QQ243 b may be the same network or networks or differentnetwork or networks. Communication subsystem QQ231 may be configured toinclude one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.11,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter QQ233 and/or receiver QQ235 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter QQ233and receiver QQ235 of each transceiver may share circuit components,software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem QQ231 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem QQ231 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network QQ243 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, networkQQ243 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source QQ213 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE QQ200.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE QQ200 or partitioned acrossmultiple components of UE QQ200. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystemQQ231 may be configured to include any of the components describedherein. Further, processing circuitry QQ201 may be configured tocommunicate with any of such components over bus QQ202. In anotherexample, any of such components may be represented by programinstructions stored in memory that when executed by processing circuitryQQ201 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components may be partitionedbetween processing circuitry QQ201 and communication subsystem QQ231. Inanother example, the non-computationally intensive functions of any ofsuch components may be implemented in software or firmware and thecomputationally intensive functions may be implemented in hardware.

FIG. 9 is a schematic block diagram illustrating a virtualizationenvironment QQ300 in which functions implemented by some embodiments maybe virtualized. In the present context, virtualizing means creatingvirtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments QQ300 hosted byone or more of hardware nodes QQ330. Further, in embodiments in whichthe virtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications QQ320(which may alternatively be called software instances, virtualappliances, network functions, virtual nodes, virtual network functions,etc.) operative to implement some of the features, functions, and/orbenefits of some of the embodiments disclosed herein. Applications QQ320are run in virtualization environment QQ300 which provides hardwareQQ330 comprising processing circuitry QQ360 and memory QQ390. MemoryQQ390 contains instructions QQ395 executable by processing circuitryQQ360 whereby application QQ320 is operative to provide one or more ofthe features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose orspecial-purpose network hardware devices QQ330 comprising a set of oneor more processors or processing circuitry QQ360, which may becommercial off-the-shelf (COTS) processors, dedicated ApplicationSpecific Integrated Circuits (ASICs), or any other type of processingcircuitry including digital or analog hardware components or specialpurpose processors. Each hardware device may comprise memory QQ390-1which may be non-persistent memory for temporarily storing instructionsQQ395 or software executed by processing circuitry QQ360. Each hardwaredevice may comprise one or more network interface controllers (NICs)QQ370, also known as network interface cards, which include physicalnetwork interface QQ380. Each hardware device may also includenon-transitory, persistent, machine-readable storage media QQ390-2having stored therein software QQ395 and/or instructions executable byprocessing circuitry QQ360. Software QQ395 may include any type ofsoftware including software for instantiating one or more virtualizationlayers QQ350 (also referred to as hypervisors), software to executevirtual machines QQ340 as well as software allowing it to executefunctions, features and/or benefits described in relation with someembodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer QQ350 or hypervisor. Differentembodiments of the instance of virtual appliance QQ320 may beimplemented on one or more of virtual machines QQ340, and theimplementations may be made in different ways.

During operation, processing circuitry QQ360 executes software QQ395 toinstantiate the hypervisor or virtualization layer QQ350, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer QQ350 may present a virtual operating platform thatappears like networking hardware to virtual machine QQ340.

As shown in FIG. 9 , hardware QQ330 may be a standalone network nodewith generic or specific components. Hardware QQ330 may comprise antennaQQ3225 and may implement some functions via virtualization.Alternatively, hardware QQ330 may be part of a larger cluster ofhardware (e.g. such as in a data center or customer premise equipment(CPE)) where many hardware nodes work together and are managed viamanagement and orchestration (MANO) QQ3100, which, among others,oversees lifecycle management of applications QQ320.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine QQ340 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines QQ340, and that part of hardware QQ330 that executes thatvirtual machine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines QQ340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines QQ340 on top of hardware networking infrastructureQQ330 and corresponds to application QQ320 in FIG. 9 .

In some embodiments, one or more radio units QQ3200 that each includeone or more transmitters QQ3220 and one or more receivers QQ3210 may becoupled to one or more antennas QQ3225. Radio units QQ3200 maycommunicate directly with hardware nodes QQ330 via one or moreappropriate network interfaces and may be used in combination with thevirtual components to provide a virtual node with radio capabilities,such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use ofcontrol system QQ3230 which may alternatively be used for communicationbetween the hardware nodes QQ330 and radio units QQ3200.

With reference to FIG. 10 , in accordance with an embodiment, acommunication system includes telecommunication network QQ410, such as a3GPP-type cellular network, which comprises access network QQ411, suchas a radio access network, and core network QQ414. Access network QQ411comprises a plurality of base stations QQ412 a, QQ412 b, QQ412 c, suchas NBs, eNBs, gNBs or other types of wireless access points, eachdefining a corresponding coverage area QQ413 a, QQ413 b, QQ413 c. Eachbase station QQ412 a, QQ412 b, QQ412 c is connectable to core networkQQ414 over a wired or wireless connection QQ415. A first UE QQ491located in coverage area QQ413 c is configured to wirelessly connect to,or be paged by, the corresponding base station QQ412 c. A second UEQQ492 in coverage area QQ413 a is wirelessly connectable to thecorresponding base station QQ412 a. While a plurality of UEs QQ491,QQ492 are illustrated in this example, the disclosed embodiments areequally applicable to a situation where a sole UE is in the coveragearea or where a sole UE is connecting to the corresponding base stationQQ412.

Telecommunication network QQ410 is itself connected to host computerQQ430, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer QQ430 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections QQ421 and QQ422 between telecommunication network QQ410 andhost computer QQ430 may extend directly from core network QQ414 to hostcomputer QQ430 or may go via an optional intermediate network QQ420.Intermediate network QQ420 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network QQ420,if any, may be a backbone network or the Internet; in particular,intermediate network QQ420 may comprise two or more sub-networks (notshown).

The communication system of FIG. 10 as a whole enables connectivitybetween the connected UEs QQ491, QQ492 and host computer QQ430. Theconnectivity may be described as an over-the-top (OTT) connection QQ450.Host computer QQ430 and the connected UEs QQ491, QQ492 are configured tocommunicate data and/or signaling via OTT connection QQ450, using accessnetwork QQ411, core network QQ414, any intermediate network QQ420 andpossible further infrastructure (not shown) as intermediaries. OTTconnection QQ450 may be transparent in the sense that the participatingcommunication devices through which OTT connection QQ450 passes areunaware of routing of uplink and downlink communications. For example,base station QQ412 may not or need not be informed about the pastrouting of an incoming downlink communication with data originating fromhost computer QQ430 to be forwarded (e.g., handed over) to a connectedUE QQ491. Similarly, base station QQ412 need not be aware of the futurerouting of an outgoing uplink communication originating from the UEQQ491 towards the host computer QQ430.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 11 . In communicationsystem QQ500, host computer QQ510 comprises hardware QQ515 includingcommunication interface QQ516 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of communication system QQ500. Host computer QQ510 furthercomprises processing circuitry QQ518, which may have storage and/orprocessing capabilities. In particular, processing circuitry QQ518 maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer QQ510further comprises software QQ511, which is stored in or accessible byhost computer QQ510 and executable by processing circuitry QQ518.Software QQ511 includes host application QQ512. Host application QQ512may be operable to provide a service to a remote user, such as UE QQ530connecting via OTT connection QQ550 terminating at UE QQ530 and hostcomputer QQ510. In providing the service to the remote user, hostapplication QQ512 may provide user data which is transmitted using OTTconnection QQ550.

Communication system QQ500 further includes base station QQ520 providedin a telecommunication system and comprising hardware QQ525 enabling itto communicate with host computer QQ510 and with UE QQ530. HardwareQQ525 may include communication interface QQ526 for setting up andmaintaining a wired or wireless connection with an interface of adifferent communication device of communication system QQ500, as well asradio interface QQ527 for setting up and maintaining at least wirelessconnection QQ570 with UE QQ530 located in a coverage area (not shown inFIG. 11 ) served by base station QQ520. Communication interface QQ526may be configured to facilitate connection QQ560 to host computer QQ510.Connection QQ560 may be direct or it may pass through a core network(not shown in FIG. 11 ) of the telecommunication system and/or throughone or more intermediate networks outside the telecommunication system.In the embodiment shown, hardware QQ525 of base station QQ520 furtherincludes processing circuitry QQ528, which may comprise one or moreprogrammable processors, application-specific integrated circuits, fieldprogrammable gate arrays or combinations of these (not shown) adapted toexecute instructions. Base station QQ520 further has software QQ521stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referredto. Its hardware QQ535 may include radio interface QQ537 configured toset up and maintain wireless connection QQ570 with a base stationserving a coverage area in which UE QQ530 is currently located. HardwareQQ535 of UE QQ530 further includes processing circuitry QQ538, which maycomprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. UE QQ530 furthercomprises software QQ531, which is stored in or accessible by UE QQ530and executable by processing circuitry QQ538. Software QQ531 includesclient application QQ532. Client application QQ532 may be operable toprovide a service to a human or non-human user via UE QQ530, with thesupport of host computer QQ510. In host computer QQ510, an executinghost application QQ512 may communicate with the executing clientapplication QQ532 via OTT connection QQ550 terminating at UE QQ530 andhost computer QQ510. In providing the service to the user, clientapplication QQ532 may receive request data from host application QQ512and provide user data in response to the request data. OTT connectionQQ550 may transfer both the request data and the user data. Clientapplication QQ532 may interact with the user to generate the user datathat it provides.

It is noted that host computer QQ510, base station QQ520 and UE QQ530illustrated in FIG. 11 may be similar or identical to host computerQQ430, one of base stations QQ412 a, QQ412 b, QQ412 c and one of UEsQQ491, QQ492 of FIG. 10 , respectively. This is to say, the innerworkings of these entities may be as shown in FIG. 11 and independently,the surrounding network topology may be that of FIG. 10 .

In FIG. 11 , OTT connection QQ550 has been drawn abstractly toillustrate the communication between host computer QQ510 and UE QQ530via base station QQ520, without explicit reference to any intermediarydevices and the precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE QQ530 or from the service provider operating host computerQQ510, or both. While OTT connection QQ550 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE QQ530 using OTT connectionQQ550, in which wireless connection QQ570 forms the last segment. Moreprecisely, the teachings of these embodiments may improve the data rateachievable by a UE connected to a base station operating in accordancewith the methods disclosed herein, and thereby provide benefits such asreduced user waiting time, relaxed restriction on file size, betterresponsiveness, extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection QQ550 between hostcomputer QQ510 and UE QQ530, in response to variations in themeasurement results. The measurement procedure and/or the networkfunctionality for reconfiguring OTT connection QQ550 may be implementedin software QQ511 and hardware QQ515 of host computer QQ510 or insoftware QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments,sensors (not shown) may be deployed in or in association withcommunication devices through which OTT connection QQ550 passes; thesensors may participate in the measurement procedure by supplying valuesof the monitored quantities exemplified above, or supplying values ofother physical quantities from which software QQ511, QQ531 may computeor estimate the monitored quantities. The reconfiguring of OTTconnection QQ550 may include message format, retransmission settings,preferred routing etc.; the reconfiguring need not affect base stationQQ520, and it may be unknown or imperceptible to base station QQ520.Such procedures and functionalities may be known and practiced in theart. In certain embodiments, measurements may involve proprietary UEsignaling facilitating host computer QQ510's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software QQ511 and QQ531 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection QQ550 while it monitors propagation times, errors etc.

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to Figures QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG. 12will be included in this section. In step QQ610, the host computerprovides user data. In substep QQ611 (which may be optional) of stepQQ610, the host computer provides the user data by executing a hostapplication. In step QQ620, the host computer initiates a transmissioncarrying the user data to the UE. In step QQ630 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step QQ640 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 13 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to Figures QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG. 13will be included in this section. In step QQ710 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In stepQQ720, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step QQ730 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 14 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to Figures QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FigureFIG. 14 will be included in this section. In step QQ810 (which may beoptional), the UE receives input data provided by the host computer.Additionally or alternatively, in step QQ820, the UE provides user data.In substep QQ821 (which may be optional) of step QQ820, the UE providesthe user data by executing a client application. In substep QQ811 (whichmay be optional) of step QQ810, the UE executes a client applicationwhich provides the user data in reaction to the received input dataprovided by the host computer. In providing the user data, the executedclient application may further consider user input received from theuser. Regardless of the specific manner in which the user data wasprovided, the UE initiates, in substep QQ830 (which may be optional),transmission of the user data to the host computer. In step QQ840 of themethod, the host computer receives the user data transmitted from theUE, in accordance with the teachings of the embodiments describedthroughout this disclosure.

FIG. 15 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to Figures QQ4 and QQ5. Forsimplicity of the present disclosure, only drawing references to FIG. 15will be included in this section. In step QQ910 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep QQ920 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In stepQQ930 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

ABBREVIATIONS

At least some of the following abbreviations may be used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

-   1×RTT CDMA2000 1×Radio Transmission Technology-   3GPP 3rd Generation Partnership Project-   5G 5th Generation-   ABS Almost Blank Subframe-   ARQ Automatic Repeat Request-   AWGN Additive White Gaussian Noise-   BCCH Broadcast Control Channel-   BCH Broadcast Channel-   CA Carrier Aggregation-   CC Carrier Component-   CCCH SDU Common Control Channel SDU-   CDMA Code Division Multiplexing Access-   CGI Cell Global Identifier-   CIR Channel Impulse Response-   CP Cyclic Prefix-   CPICH Common Pilot Channel-   CPICH Ec/No CPICH Received energy per chip divided by the power    density in the band-   CQI Channel Quality information-   C-RNTI Cell RNTI-   CSI Channel State Information-   DCCH Dedicated Control Channel-   DL Downlink-   DM Demodulation-   DMRS Demodulation Reference Signal-   DRX Discontinuous Reception-   DTX Discontinuous Transmission-   DTCH Dedicated Traffic Channel-   DUT Device Under Test-   E-CID Enhanced Cell-ID (positioning method)-   E-SMLC Evolved-Serving Mobile Location Centre-   ECGI Evolved CGI-   eNB E-UTRAN NodeB-   ePDCCH enhanced Physical Downlink Control Channel-   E-SMLC evolved Serving Mobile Location Center-   E-UTRA Evolved UTRA-   E-UTRAN Evolved UTRAN-   FDD Frequency Division Duplex-   FFS For Further Study-   GERAN GSM EDGE Radio Access Network-   gNB Base station in NR-   GNSS Global Navigation Satellite System-   GSM Global System for Mobile communication-   HARQ Hybrid Automatic Repeat Request-   HO Handover-   HSPA High Speed Packet Access-   HRPD High Rate Packet Data-   IAB Integrated access and backhaul-   LOS Line of Sight-   LPP LTE Positioning Protocol-   LTE Long-Term Evolution-   MAC Medium Access Control-   MBMS Multimedia Broadcast Multicast Services-   MBSFN Multimedia Broadcast multicast service Single Frequency    Network-   MBSFN ABS MBSFN Almost Blank Subframe-   MDT Minimization of Drive Tests-   MIB Master Information Block-   MME Mobility Management Entity-   MSC Mobile Switching Center-   MT Mobile termination-   NPDCCH Narrowband Physical Downlink Control Channel-   NR New Radio-   OCNG OFDMA Channel Noise Generator-   OFDM Orthogonal Frequency Division Multiplexing-   OFDMA Orthogonal Frequency Division Multiple Access-   OSS Operations Support System-   OTDOA Observed Time Difference of Arrival-   O&M Operation and Maintenance-   PBCH Physical Broadcast Channel-   P-CCPCH Primary Common Control Physical Channel-   PCell Primary Cell-   PCFICH Physical Control Format Indicator Channel-   PDCCH Physical Downlink Control Channel-   PDP Profile Delay Profile-   PDSCH Physical Downlink Shared Channel-   PGW Packet Gateway-   PHICH Physical Hybrid-ARQ Indicator Channel-   PLMN Public Land Mobile Network-   PMI Precoder Matrix Indicator-   PRACH Physical Random Access Channel-   PRS Positioning Reference Signal-   PSS Primary Synchronization Signal-   PUCCH Physical Uplink Control Channel-   PUSCH Physical Uplink Shared Channel-   RACH Random Access Channel-   QAM Quadrature Amplitude Modulation-   RAN Radio Access Network-   RAT Radio Access Technology-   RLM Radio Link Management-   RMSI Remaining Minimum System Information-   RNC Radio Network Controller-   RNTI Radio Network Temporary Identifier-   RRC Radio Resource Control-   RRM Radio Resource Management-   RS Reference Signal-   RSCP Received Signal Code Power-   RSRP Reference Symbol Received Power OR Reference Signal Received    Power-   RSRQ Reference Signal Received Quality OR Reference Symbol Received    Quality-   RSSI Received Signal Strength Indicator-   RSTD Reference Signal Time Difference-   SCH Synchronization Channel-   SCell Secondary Cell-   SDU Service Data Unit-   SFN System Frame Number-   SGW Serving Gateway-   SI System Information-   SIB System Information Block-   SNR Signal to Noise Ratio-   SON Self Optimized Network-   SS Synchronization Signal-   SSB SS/PBCH block comprises of PSS, SSS, and PBCH including the DMRS    for the PBCH-   SSS Secondary Synchronization Signal-   TDD Time Division Duplex-   TDOA Time Difference of Arrival-   TOA Time of Arrival-   TSS Tertiary Synchronization Signal-   TTI Transmission Time Interval-   UE User Equipment-   UL Uplink-   UMTS Universal Mobile Telecommunication System-   USIM Universal Subscriber Identity Module-   UTDOA Uplink Time Difference of Arrival-   UTRA Universal Terrestrial Radio Access-   UTRAN Universal Terrestrial Radio Access Network-   WCDMA Wide CDMA-   WLAN Wide Local Area Network

The invention claimed is:
 1. A method performed at an integrated accessand backhaul (IAB) node, comprising: during the IAB node initial accessto a first parent IAB node, wherein the IAB node firstly join an IABbackhaul link, assuming a predetermined synchronization signal block(SSB) transmission periodicity; searching an SSB at the predeterminedSSB transmission periodicity; and getting access to the first parent IABnode according to the searched SSB.
 2. The method of claim 1, furthercomprising: receiving system information from the first parent IAB node,according to the searched SSB; and obtaining actual SSB transmissionperiodicity from the received system information.
 3. The method of claim2, wherein the searching an SSB at the predetermined SSB transmissionperiodicity comprises, searching a set of SSBs at the predetermined SSBtransmission periodicity regardless of periodicity information on SSBsindicated in a broadcast signal.
 4. The method of claim 3, wherein theSSBs indicated by the obtained actual SSB transmission periodicity arefor specific use in an IAB backhaul link.
 5. The method of claim 3,wherein the SSBs indicated by the obtained actual SSB transmissionperiodicity are reusing a same set of SSBs used for access UEs.
 6. Themethod of claim 2, when the IAB backhaul link between the IAB node andthe first parent IAB node get failure, further comprising: searching anSSB at the obtained actual periodicity of SSBs; and getting initialaccess to a second parent IAB node, wherein the second parent IAB nodediffers from the first parent IAB node.
 7. The method of claim 1,wherein the IAB node is under a non-standalone (NSA) deployment.
 8. Amethod performed at an integrated access and backhaul (IAB) node,comprising: during the IAB node initial access to a parent IAB node,determining its availability of synchronization signal block (SSB)transmission periodicity; upon determining there is no information onactual SSB transmission periodicity in the IAB node, assuming a defaultSSB transmission periodicity; searching an SSB at the default SSBtransmission periodicity.
 9. The method of claim 8, further comprising:upon determining an actual SSB transmission periodicity is available inthe IAB node, searching an SSB at the actual SSB transmissionperiodicity.
 10. The method of claim 9, wherein SSBs indicated by theactual SSB transmission periodicity are for specific use in an IABbackhaul link.
 11. The method of claim 9, wherein SSBs indicated by theactual SSB transmission periodicity are reusing a same set of SSBs usedfor access UEs.
 12. The method of claim 8, wherein the determining itsavailability of SSB transmission periodicity by the IAB node is afeedback to a failure of IAB backhaul link between the IAB node and itsparent IAB node.
 13. The method of claim 8, wherein the IAB node isunder a non-standalone (NSA) deployment.
 14. An integrated access andbackhaul (IAB) node, comprising: processing circuitry configured toexecute program code stored in the memory, cause the IAB node to: duringthe IAB node initial access to a first parent IAB node, wherein the IABnode firstly join an IAB backhaul link, assume a predeterminedsynchronization signal block (SSB) transmission periodicity; search anSSB at the predetermined SSB transmission periodicity; and get access tothe first parent IAB node according to the searched SSB.
 15. The IABnode according to claim 14, wherein the memory further includesinstructions with, when executed by the processing circuitry, cause theIAB node to: receive system information from the first parent IAB node,according to the searched SSB; and obtain actual SSB transmissionperiodicity from the received system information.
 16. The IAB nodeaccording to claim 15, wherein the memory further includes instructionswith, when executed by the processing circuitry, cause the IAB node to:when the IAB backhaul link between the IAB node and the first parent IABnode get failure, search an SSB at the obtained actual periodicity ofSSBs; and get initial access to a second parent IAB node, wherein thesecond parent IAB node differs from the first parent IAB node.
 17. TheIAB node according to claim 15, wherein the SSBs indicated by theobtained actual SSB transmission periodicity are for specific use in anIAB backhaul link.
 18. The IAB node according to claim 15, wherein theSSBs indicated by the obtained actual SSB transmission periodicity arereusing a same set of SSBs used for access UEs.
 19. The IAB nodeaccording to claim 14, wherein the IAB node is under an NSA deployment.